-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd: add dvc update --to-remote docs #2175
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trying to understand the semantics first, to see how to write it down properly.
Co-authored-by: Jorge Orpinel <[email protected]>
Hey @shcheklein @jorgeorpinel are we missing anything on this? |
- `--to-remote` - update the import `.dvc` file and | ||
[transfer](/doc/command-reference/import-url#example-import-straight-to-the-remote) | ||
the new data directly to remote storage (the default one unless `-r` is used). | ||
No changes are done in the <abbr>workspace</abbr>. Use `dvc pull` to get the | ||
data locally. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We forgot to mention that this only works for import-url
imports @isidentical — per iterative/dvc/pull/5475
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
p.s. can you update --to-remote
data import-url
ed without --to-remote
? I assume there's no restriction to do so but just curious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
p.s. can you update --to-remote data import-urled without --to-remote
yes
❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention
Fix #issue
(if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏